Skip to main content

Security Overrides

You can employ a single password override system or you can employ a user-based override system. The user-based system is more secure and includes logging whereas the single password system is much less strict.

Invoicing Variables​

The left image shows the user-based override system where User Security settings control who can override what; the right image shows the single password override system.

img

User Security​

img

In the overrides section of user security, you establish which overrides the individual users have security for. If you have override security in an area, you will still be prompted but you will not have to type in your user ID and password to override.

Invoicing​

img

Most of the override securities are focused around the invoicing system. In the example above, the user is attempting to schedule a COD invoice with a balance owing.

The user name and password are greyed out, which indicates that the user signed into EPASS has security to override this situation, so all it is asking for is a reason.

img

In this case, the user logged into EPASS does not have override security to schedule a COD invoice with a balance owing and so we must get somebody with the correct security level to type in their user ID, password and then a reason.

Notepad​

img

In the notepad, you will see a system generated note with the date, time, user details, and the reason. The user ID on the notepad is the person who gave the override.